Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update tools.json #3512

Merged
merged 1 commit into from
Dec 23, 2024
Merged

chore: update tools.json #3512

merged 1 commit into from
Dec 23, 2024

Conversation

asyncapi-bot
Copy link
Contributor

@asyncapi-bot asyncapi-bot commented Dec 23, 2024

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • New Features

    • Added support for the new technology "amqp" with updated color and border styles.
    • Introduced new tools such as nestjs-asyncapi and templates like Node.js Multiprotocol Template and Java Template.
  • Bug Fixes

    • Updated existing tool names and descriptions for clarity and accuracy, including the transition from Zod Sockets to SIO-AsyncAPI.
  • Documentation

    • Revised descriptions and links for tools and templates to reflect their new functionalities and categories.

Copy link

coderabbitai bot commented Dec 23, 2024

Walkthrough

The pull request introduces modifications to two configuration files: config/all-tags.json and config/tools-automated.json. In all-tags.json, a new technology "amqp" is added, and multiple existing technologies have their color schemes updated to a consistent blue palette. The tools-automated.json file undergoes significant restructuring, with changes to tool categories, additions of new tools like nestjs-asyncapi, and renaming/updating of existing tools across different AsyncAPI-related categories.

Changes

File Changes
config/all-tags.json - Added new technology "amqp"
- Updated color schemes for 20+ technologies to bg-[#61d0f2] and border-[#40ccf7]
config/tools-automated.json - Added nestjs-asyncapi in Code-first tools
- Replaced Zod Sockets with SIO-AsyncAPI
- Updated tool categories and descriptions
- Added Node.js Multiprotocol Template and Java Template
- Renamed and restructured various AsyncAPI generator templates

Suggested labels

autoapproved, autoupdate

Suggested reviewers

  • derberg
  • magicmatatjahu
  • devilkiller-ag
  • akshatnema
  • sambhavgupta0705
  • anshgoyalevil
  • Mayaleeeee
  • asyncapi-bot-eve

Poem

🐰 A rabbit's tale of config delight,
Colors shifting, tools taking flight!
AMQP joins the tech parade,
AsyncAPI's landscape remade,
With blue hues bright and spirits light! 🌈


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

netlify bot commented Dec 23, 2024

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit 8a847d5
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/6768b01008063c0008db104b
😎 Deploy Preview https://deploy-preview-3512--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

codecov bot commented Dec 23, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.59%. Comparing base (2327eae) to head (8a847d5).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3512   +/-   ##
=======================================
  Coverage   86.59%   86.59%           
=======================================
  Files          21       21           
  Lines         664      664           
=======================================
  Hits          575      575           
  Misses         89       89           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@asyncapi-bot
Copy link
Contributor Author

⚡️ Lighthouse report for the changes in this PR:

Category Score
🔴 Performance 33
🟢 Accessibility 98
🟢 Best practices 92
🟢 SEO 100
🔴 PWA 33

Lighthouse ran on https://deploy-preview-3512--asyncapi-website.netlify.app/

@asyncapi-bot asyncapi-bot merged commit 3afcf6a into master Dec 23, 2024
33 of 34 checks passed
@asyncapi-bot asyncapi-bot deleted the update-tools/regenerateTools branch December 23, 2024 00:38
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🔭 Outside diff range comments (1)
config/tools-automated.json (1)

Line range hint 721-736: Inconsistent language specification in templates

The Java Template specifies "javascript" as its language, which appears to be incorrect given it's a Java template.

Apply this fix:

  "filters": {
    "language": [
-     "javascript"
+     "java"
    ],

Also applies to: 739-756

🧹 Nitpick comments (3)
config/all-tags.json (1)

1-1: Improve JSON file readability

The file is currently formatted as a single line, which makes it difficult to read and maintain. Consider formatting the JSON with proper indentation.

-{"languages":[{"name":"Go/Golang"...}]}
+{
+  "languages": [
+    {
+      "name": "Go/Golang",
+      ...
+    }
+  ]
+}
config/tools-automated.json (2)

516-531: Update AsyncAPI Validation description

The description could be more detailed to explain what types of validation are supported (schema validation, message validation, etc.).


Line range hint 799-814: Consider updating HTML Template technology tags

Since the template uses AsyncAPI React component, consider adding "React JS" to the technology list for better discoverability.

  "technology": [
-   "HTML"
+   "HTML",
+   "React JS"
  ],
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2327eae and 8a847d5.

📒 Files selected for processing (2)
  • config/all-tags.json (1 hunks)
  • config/tools-automated.json (12 hunks)
🔇 Additional comments (3)
config/all-tags.json (1)

1-1: Consistent color scheme update looks good

The standardization of colors (bg-[#61d0f2] and border-[#40ccf7]) across multiple technologies improves visual consistency. The addition of the "amqp" technology aligns well with the tools updates in tools-automated.json.

config/tools-automated.json (2)

52-70: New nestjs-asyncapi tool entry looks good

The new tool entry is well-structured with appropriate categorization and clear description.


143-166: Verify ZenWave SDK categorization

The tool appears in multiple categories (Code Generators, DSL, CLIs). While this might be intentional as it serves multiple purposes, please verify if all categories are still applicable after recent changes.

✅ Verification successful

Based on the search results, I can see that ZenWave SDK appears consistently in the tools list with the following categories:

  • code-generator
  • dsl
  • mocking-and-testing
  • cli

The tool is properly categorized as it serves multiple purposes:

  1. Code Generator: It generates code for Spring Cloud Streams from AsyncAPI specifications
  2. DSL: It provides Domain-Specific Language support with JHipster JDL integration
  3. Mocking and Testing: It includes testing capabilities for Event-Driven Microservices
  4. CLI: It offers command-line interface functionality

The categorization is accurate and consistent with the tool's features and capabilities as shown in its description: "DDD and API-First for Event-Driven Microservices" and its technology stack including Maven, Spring Cloud Streams, and JHipster JDL.

All categories are correctly applied and verified

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for all occurrences of ZenWave SDK to ensure consistent categorization
rg -A 20 "ZenWave SDK" --json | jq -r '.data.lines.text' | grep -E "title|categories"

Length of output: 51953

Comment on lines +94 to 113
"title": "SIO-AsyncAPI",
"description": "This is code-first approach to generate AsyncAPI specification from Socket.IO server.",
"links": {
"websiteUrl": "https://www.npmjs.com/package/zod-sockets",
"repoUrl": "https://github.com/RobinTail/zod-sockets"
"websiteUrl": "https://github.com/daler-rahimov/sio-asyncapi",
"docsUrl": "https://github.com/daler-rahimov/sio-asyncapi",
"repoUrl": "https://github.com/daler-rahimov/sio-asyncapi"
},
"filters": {
"language": "TypeScript",
"language": "Python",
"technology": [
"Node.js",
"TypeScript"
"Socket.IO",
"Flask"
],
"categories": [
"code-first",
"dsl",
"framework"
"api"
],
"hasCommercial": false,
"isAsyncAPIOwner": false
}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Duplicate tool entry detected

The "SIO-AsyncAPI" tool appears twice in the file - once in the "APIs" section and once in "Code-first tools". Consider keeping it in the most appropriate category and removing the duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants